home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941221-19950208
/
000342_news@columbia.edu_Mon Jan 30 08:19:16 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA23479
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 1 Feb 1995 06:02:46 -0500
Received: by apakabar.cc.columbia.edu id AA26312
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 1 Feb 1995 06:02:45 -0500
Path: news.columbia.edu!panix!news.mathworks.com!hookup!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MSKermit Login Problem
Message-Id: <1995Jan30.141916.39821@cc.usu.edu>
Date: 30 Jan 95 14:19:16 MDT
References: <9501291851.AA22159@swcscmd-fs>
Organization: Utah State University
Lines: 53
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <9501291851.AA22159@swcscmd-fs>, dtd-lo3@usasoc.soc.mil (Mr. Calvin Rome) writes:
> I need some help getting MSKermit to login to a UNIX platform
> running SUNOS 4.1.
>
> Here is the situation:
>
> I am currently using MSKermit v3.14 dated 18 Jan 95, patch level 3.
> I had been using MSKermit v3.13 to login to a UNIX platform running
> SCO and to the NOW troubled SUN connection without any problems. In
> the meantime I began using the MSKermit betas as they were being
> released and making minor modifications in the *.ini files. The Sys
> Admin on the Sun box made some changes in the login scripts which
> broke the ability of MSKermit to login. I went back to my original
> MSK v3.13 program and tried (I had left everything intact during beta
> testing) and it would not login either. HOWEVER, I have also been
> using both Procomm Plus for DOS and Procomm Plus for Win, both of
> which login to the SUN box with no problems. My userid is dtd-lo3.
> When attempting to login with MSK this is what appears at the login:
>
> login: t-lo3 then it locks up
>
> Just to see what happens I used Caps and this was the result:
>
> login: DD-3 then it locks up
>
> With Procomm I get normal results and am then prompted for the
> password:
>
> login: dtd-lo3
> Password:
>
> My Sys Admin's solution is to use Procomm! But I like MSK much better
> for connecting to the UNIX boxes and then on to Internet. Any
> suggestions?
>
> **********************************************************************
> Calvin Rome, GS-11 | SOF Language Office
> Computer Specialist | US Army John F. Kennedy Special Warfare Center
> dtd-lo3@usasoc.soc.mil | and School
> ***********************************************************************
-------------
SET TCP DEBUG ON to see Telnet Options negotiations blow by blow.
The above has the indications of an Option your host wants but is not
supported by MSK. LOG SESSION if you want us to have a look at it too
(or give me a host name to try from my place).
Another, related, thought it your host may require LF as a terminator
rather than CR during the login process. Try ending lines in Control-J to
see.
Last thought is your host may not understand terminal type VT320
and it keeps asking for something different. This will show in the Options
negotiations chatter. SET TCP TERM-TYPE is the way to say one thing and
be another.
Joe D.